home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Collection of Tools & Utilities
/
Collection of Tools and Utilities.iso
/
network
/
netlis13.zip
/
NETLIST.DOC
< prev
next >
Wrap
Text File
|
1990-06-12
|
42KB
|
1,190 lines
[*]===========================================================[*]
| |
| NETLIST Concurrent search for NetBIOS network users, |
| 1.3 extended network statistics |
| June 1990 & other services |
| |
[*]===========================================================[*]
Public domain software
by Adam MIROWSKI
MIROWSKI@FRECP12.BITNET
ADAMAINT@FRECP12.BITNET
developed at the
Ecole Centrale de Paris
FRANCE
=======================
TABLE of CONTENTS
=======================
INTRODUCTION
------------
NETLIST's purpose
Prerequisites
New version 1.3 features
Version 1.2 features
USER's GUIDE
------------
NETLIST's command line syntax
Explanation of various fields and entities
Creating users' database
NETLIST.DEF, the configuration file
Examples
Starting and interrupting NETLIST
Archive's contents
Remarks -- Bugs
APPENDICES
----------
NETSTART.COM
Ideas for next releases
Search's principles
Connection's mechanism
The author
==============
INTRODUCTION
==============
__________________
NETLIST's purpose
NETLIST performs various tests on NetBIOS networks. NetBIOS protocols
are mainly run on Token-Ring and PC Network hardware, but there are
implementations over TCP/IP and AppleTalk.
NETLIST can:
-- show current network users, by quickly checking the presence of
a list of selected users, doing up to 170 tests per second,
-- scan a range of adapters by number, to show connected ones,
-- give extensive information and usage statistics about any adapter
on the network,
-- give an explanation about NetBIOS return codes.
User's list can be automatically created and later updated. Results
can be automatically time-stamped and archived.
NETLIST supports two simultaneous LAN adapters.
_____________
Prerequisites
Have a working NetBIOS driver
-----------------------------
All tests are performed at the NetBIOS level of protocols, so in
order to be detected or tested, the user must have an installed and
working NetBIOS that could answer NETLIST. The machine on which
NETLIST is run must have NetBIOS too.
The NetBIOS layer will be active on a machine if one of the following
network softwares is running:
-- IBM PC-LAN (Microsoft Network, in MS-Windows 3.0 terminology)
-- Da Vinci eMAIL
-- Future Soft DynaComm
-- Sun Microsystems TOPS (*)
-- Novell NetWare (*)
-- Microsoft/3Com LAN Manager
and generally if any NetBIOS based software has been used since the
boot.
(*) Netware and TOPS aren't NetBIOS based networking softwares, but
they can provide NetBIOS services if the respective drivers have
been loaded. You will only be able to detect people who did that.
TOPS' NetBIOS driver is TNETBIOS.EXE and should be loaded after
ALAP and PSTACK. You should add the /... parameter on ALAP command
line.
Netware's driver is NETBIOS.EXE. It should be loaded after IPX.COM
or after NET?.COM.
IBM's dxmT0mod.sys NetBIOS driver isn't automatically activated on
adapter opening, except when it opens the adapter itself. So you
don't have an active NetBIOS layer if after the boot you only
started:
-- IBM PC-3270 emulation,
-- IBM Token-Ring bridge program,
-- IBM TCP/IP suite of programs,
-- IBMTOKEN.COM (Brian Fisher's 'Ethernet' packet driver
for TCP/IP over Token-Ring).
However, running NETLIST will activate your NetBIOS layer after
the start of the PC-3270 emulation or after the installation of
IBMTOKEN.COM. NETLIST cannot however activate NetBIOS on remote
adapters.
To simply start the NetBIOS layer there is NETSTART.COM, that you
could insert at the end of batch files used to launch non NetBIOS-
based network applications.
Have a database of users or an momentaneous access to network machines
----------------------------------------------------------------------
In order to detect the presence of a user or to test his adapter, you
have to know either one of the network names declared by his NetBIOS
network software (for exemple the name PC-LAN has been started with)
or the permanent identification number of his adapter.
Testing adapter numbers is better than testing names, because an
adapter number will be present on the network as soon as NetBIOS is
started, whereas network names can change and depend on the currently
used software.
The adapter number can be obtained with NETLIST either remotely, from
an active name or locally, running NETLIST on the machine the adapter
is installed in.
To create users' database, run REGISTER.BAT from a diskette on each
machine you want to register. You will be asked to input a few words
to identify the current machine. See details below.
________________________
New version 1.3 features
Describes remote adapters better...
-----------------------------------
-- NETLIST shows whether PC-LAN is running on remote adapters.
-- The /X option displays all the names found on adapters during
a search or in a scan.
-- Adapter status display has been adapted to new NetBIOS drivers.
Now, it indicates the type of the adapter hardware. Various
other fields have been changed.
Is easier to use...
-------------------
-- Configuration files set defaults. No more need for batch files.
-- User's database can be set up with a minimal effort.
-- The /F option has a default argument (NETLIST.NAM). The /S option
is more intelligent.
-- Now when NETLIST doesn't find a name or an adapter number, it
clearly indicates how it understood the given input string.
-- Name and adapter number syntaxes are better checked.
-- Now slash syntax for funny chars in names is used as often as
possible, except when saving screen place is important. No
slash is put in front of adapter numbers when there is no need
for it.
...and more powerful!
---------------------
-- Every command updates the specified or default namefile if /U
option is specified.
-- The /R [times] options asks to loop the test continuously or
"times" times.
-- The monitor option (/M) asks NETLIST to both:
-- clear the screen and start displaying from the top,
-- display received and transmitted frames instead of adapter
numbers.
-- Adaptative use of adapter resources will try to recover from
errors which caused a premature end in the 1.2 version.
-- NETLIST tries to find the right interrupt to use. You can impose
an interrupt if needed.
Some (small) 1.2 bugs have been fixed:
--------------------------------------
-- Doesn't display inopportune messages anymore when used with 4DOS,
the COMMAND.COM replacement.
-- Missing newlines in /D option display.
-- Missing fourth digit in the displayed adapter numbers' range
(/S option).
-- Number of available NCBs on remote adapters was +1 than what
it should be.
-- Wasn't correctly working from the root directory.
____________________
Version 1.2 features
-- NETLIST can scan a given interval of adapter adresses.
-- It can automatically update the network names and adapters'
identifiers database, replacing NetBIOS names with adapter
identifiers.
-- NETLIST can display the full status of any given adapter and
the status of all sessions on the local one.
-- When NETLIST has to open the adapter, it warns about the additio-
nal (10 second) delay and gives some feedback by displaying dots
at 1/2 second intervals during the process.
-- The parameters of the search (speed, precision) can be adjusted
thro